@aulemahal @Zeitsperre Feel free to work directly on this branch and to change/remove what I've done. Once we're happy with the formatting, we'll merge it and I'll start making real unit tests.

What I'm uploading here is a version that uses test_timeseries and hits pretty much all of climatological_mean. Since this is the best time to establish a format, I'm open to all suggestions!

Deux questionnements spécifiques:

• Est-ce que test_all_default/test_options est correct ? Est-ce que je devrais les combiner en une seule grosse fonction qui teste à la fois les défauts et options ? Est-ce que je devrais au contraire séparer chaque option dans son propre test ?
• Je dois redéclarer les mêmes timeseries plusieurs fois. Serait-ce mieux de les déclarer au tout début, en variable globale (ou à l'intérieur de TestClimatologicalMean) ?

 @RondeauG
Please see the changes introduced in my latest commit.

• Instead of looping inside the test function, I used pytest.mark.parametrize. The benefit here is that if a single element fails:
  • The others are also run
  • The pytest error output specifies the exact element causing the bug
  • And we can run a single element by hand if needed, while debugging.
• I switched to conventionnal assert when we are comparing scalars.
• I rewrote a check with a set logic instead of an all of a in comprehension list.
• Rewrote the calendar check to use only xarray properties and pytest parametrize

This should be good for review.